<?php
/**
 * <https://y.st./>
 * Copyright © 2019 Alex Yst <mailto:copyright@y.st>
 * 
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program. If not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'<{title}>' => 'Improving my penmanship',
	'takedown' => '2017-11-01',
	'<{body}>' => <<<END
<img src="/img/CC_BY-SA_4.0/y.st./weblog/2019/02/19.jpg" alt="Bare bushes with bright, orange branches" class="framed-centred-image" width="649" height="480"/>
<section id="religion">
	<h2>Religion</h2>
	<p>
		<a href="https://www.gotquestions.org/Jehovah.html">It seems that &quot;Jehovah&quot; is likely a poor translation of Yahweh&apos;s original Hebrew name.</a>
		I had no idea.
		I thought both &quot;Jehovah&quot; and &quot;Yahweh&quot; were both about as likely to be correct.
		The Book of Mormon uses the name &quot;Jehovah&quot; though, so I&apos;ll continue using that name in <a href="/en/religion/scripture/Mormon.xhtml">my thoughts on it</a>.
	</p>
	<p>
		I took a look at the workbook I was assigned so I could mentally prepare for the task ahead.
		I didn&apos;t plan to actually start work on it today though, as I was still finishing up my self-assigned scripture study tonight.
		It turns out there&apos;s not really much specific to do.
		About two chapters are assigned to read each week, and I&apos;m supposed to write my thoughts as I read.
		That&apos;s it.
		Though clearly, whoever wrote this book wasn&apos;t expecting students like me.
		I write a lot more than their tiny blank can hold, even for just two chapters.
		I&apos;ll probably write my notes in a text file to deal with once I get to my full read-through of the bible, then copy then into a notebook to bring to church.
	</p>
</section>
<section id="drudgery">
	<h2>Drudgery</h2>
	<p>
		My discussion post for the day:
	</p>
	<blockquote>
		<p>
			Wow.
			I hadn&apos;t even considered problems prior to having our data set in hand.
			In your pavement example, we&apos;re got to measure the current damage level of a given block of pavement, but assessing that is rather difficult to do, objectively.
			I mean, there&apos;s definitely an objective level of damage, we just can&apos;t really measure it directly.
			There&apos;s the visible damage, which itself is difficult to quantify, and there&apos;s the internal damage, and even damage on the sides and bottom, where we can&apos;t even see it.
			Damage doesn&apos;t always occur from above.
			Ice and tree roots can be important sources of wear and cracking.
			Like you said, you need some sort of measurable units, such as the $a[PSI] the remaining pavement can take without breaking in your example.
		</p>
		<p>
			I hadn&apos;t thought about linear regression as a first step, either.
			I&apos;d figured it worked better for some problems than others, but it can also justify further work where that work might not get done otherwise.
			It might not get funding, or it might not seem necessary.
		</p>
	</blockquote>
</section>
<section id="penmanship">
	<h2>Penmanship</h2>
	<p>
		I mentioned to one of my bosses that I was going to try to learn to copy their style of writing upper-case &quot;E&quot;s a while back.
		Probably just a few weeks ago, even.
		I&apos;d already told them I thought they were the fanciest-looking &quot;E&quot;s I&apos;d ever seen, but lately, I&apos;ve been trying to improve my handwriting, and I think their &quot;E&quot;s make a great model.
		Mostly, I told them in case they for some reason didn&apos;t want me to.
		Like maybe, they&apos;d think it was strange or something.
		So I wanted to give them the chance to express that before they start seeing their &quot;E&quot;s on tickets they didn&apos;t write.
		I&apos;m sure they&apos;d notice, too, as it&apos;s not a common &quot;E&quot; shape.
		I&apos;m not sure if they&apos;ve seen anyone else write like that, but <strong>*I*</strong> sure haven&apos;t.
	</p>
	<p>
		They replied that they try to make their writing rather loopy, and someone even once told them they write like an elf.
		That&apos;s a bit odd, but I&apos;d take it as a compliment.
		But anyway, I&apos;ve been aiming for a loopy look, and found adding loops and curls improved the look of my handwriting immensely.
		I&apos;m not really satisfied with the lack of curves in some of my letters though.
		I&apos;m just not sure where or how to add them.
		In fact, &quot;E&quot; was one of my problem letters.
		So I started watching for when they&apos;d write up the job board, trying to catch a glimpse of their other letters.
		I hadn&apos;t noticed anything particularly eye-catching before, but if they&apos;ve got loopy handwriting, I want to look to it for other letter examples.
		They haven&apos;t written up the job board while I&apos;ve been on duty since then though.
		I&apos;d definitely notice, as their &quot;E&quot;s are so unique, and because their name begins with one, there&apos;s always an &quot;E&quot; on the board when they write it up.
		(Everyone on-duty gets their name written on the board next to the job they&apos;re assigned for the day, so we know where everyone needs to be.)
	</p>
	<p>
		Today, they finally wrote up the board.
		I was underwhelmed though.
		Their lower-case letters are nothing special.
		I mean, they&apos;re neat and they&apos;re nice-looking, but they&apos;re just regular-looking letters.
		Of the letters I saw, they write just like I do already, except that my lower-case &quot;a&quot;s are loopier and better-looking than theirs.
		As for upper-case letters though, I got some good examples.
		I&apos;ve been trying to make my &quot;T&quot;s nice.
		They&apos;re not one of my most-problematic letters by any means, but they&apos;re lacking.
		The boss&apos;s &quot;T&quot;s capture the look I was going for though.
		And they&apos;re not even that hard to immitate.
		Their &quot;A&quot; were also of interest.
		Theirs are more angular than mine, yet they still look much nicer than mine.
		I started trying to reduce the number of angles I had, thinking that&apos;d improve the aesthetic.
		I was wrong.
		Turning as many angles into curves as I can isn&apos;t going to be my best option.
		They also had some regular-looking upper-case letters as well; in some cases, again, my upper-case letters look better than theirs.
		I guess I got my hopes up, thinking my handwriting is so terrible that someone with master penmanship help me out quite a bit.
		My handwriting has vastly improved though, so there&apos;s not as much left to correct as I tend to think.
	</p>
</section>
END
);
